@mklement0 I believe it makes sense to add a description of exception behavior in the operators.

@iSazonov: Thanks; I've added a note re error handling, operator precedence, and return, break, continue semantics: in short: it all should work the same as with the .ForEach() / .Where() methods.

Currently, we on the @PowerShell/powershell-committee think that introducing what amounts to a third (or fourth) reference to "foreach" (foreach keyword, ForEach-Object, and .ForEach()) and a second/third reference to "where" is going to confuse existing users who are already struggling with deciding which to choose.

Instead, we think it's probably a good idea to come up with some ScriptAnalyzer rules and accompanying documentation that explain why it might not be a good idea to use | ForEach-Object or | Where-Object in non-interactive scenarios. Based on the reception of these rules, the hit rate of that documentation, etc., we can make a more informed decision about whether this is necessary.

Thanks for writing this, though @mklement0. Very through provoking, and we're not opposed to ever doing it, but I am going to merge this one into the Rejected state now for posterity.